Internet Info 1997 December/Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso/ietf/urn/urn-archives/urn-ietf.archive.9610/000113_owner-urn-ietf _Fri Oct 25 12:10:15 1996.msg

Internet Message Format | 1997-02-19 | 2KB

Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id MAA28926 for urn-ietf-out; Fri, 25 Oct 1996 12:10:15 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id MAA28920 for <[e-mail]>; Fri, 25 Oct 1996 12:10:08 -0400
Received: from alpha.Xerox.COM by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
        id AA06305  (mail destined for [e-mail]); Fri, 25 Oct 96 12:09:35 -0400
Received: from golden.parc.xerox.com ([13.1.100.139]) by alpha.xerox.com with SMTP id <16805(8)>; Fri, 25 Oct 1996 09:09:22 PDT
Received: by golden.parc.xerox.com id <2759>; Fri, 25 Oct 1996 09:09:02 PDT
To: [e-mail]
Cc: [e-mail]
In-Reply-To: <[e-mail]2>
    ([e-mail])
Subject: Re: [URN] URN Syntax thoughts
From: Larry Masinter <[e-mail]>
Message-Id: <96Oct25.090902pdt."2759"@golden.parc.xerox.com>
Date: Fri, 25 Oct 1996 09:09:02 PDT
Sender: [e-mail]
Precedence: bulk
Reply-To: Larry Masinter <[e-mail]>
Errors-To: [e-mail]

> Is it so much different to back away from the 10646/UTF-8 statement in
> the syntax document and say "As part of the registration procedure, the
> character set/encoding used by a namespace shall be documented, or some
> such words to that effect."

This is completely inadequate: the user and client need to be able to
translate the thing that the user sees on the cereal boxtop (sequence
of glyphs) into what gets transmitted over the network (sequence of
octets) in an unambiguous way. The translation method can't vary
depending on the the first part of what's translated.

Larry